-
-
Notifications
You must be signed in to change notification settings - Fork 197
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upstream says don't directly call concat::setup #71
Conversation
Thanks for pointing this out and fixing! Rather than removing the test, could you replace the Also, could you update the |
Ah, just saw that the |
Sure! Adding that test now. |
Oh, no, that won't work. concat will implicitly do concat::setup, so the class exists, we just don't include it. Hmm... I guess we could leave the test in place, since that makes sure the concats are working? |
I think we should leave the test out. We're already testing the concats happening, concat::setup is an implementation detail of concat that we don't care about. |
Yeah, no need to test internals of another library. Sorry for misleading the Thanks for your work! |
Upstream says don't directly call concat::setup
On ~modern versions of concat, concat::setup isn't to be called directly, and using it logs this warning:
Concat 1.0.0 removed the need to include concat::setup, and 1.1.0 added the deprecation warning.
I removed a test that relied on this, couldn't think of where to add some, but I could if you can think of them :)